Remote monitoring and control of treatment parameters on a medical device during a medical treatment

ABSTRACT

A method comprising: establishing a wireless connection between a first medical device and a second medical device, comprising: receiving, by the first medical device, via a short-range wireless technology protocol, connection information related to the second medical device; and establishing, by the first medical device, a wireless connection with the second medical device based on the connection information.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation and claims priority under 35 U.S.C.120 to U.S. Ser. No. 16/933,664, filed on Jul. 20, 2020, which is acontinuation of U.S. Ser. No. 16/660,981, filed on Oct. 23, 2019, nowU.S. Pat. No. 10,757,192, which is a continuation of U.S. Ser. No.16/391,710, filed on Apr. 23, 2019, now U.S. Pat. No. 10,491,678, whichis a continuation of U.S. Ser. No. 16/158,378, filed on Oct. 12, 2018,now U.S. Pat. No. 10,305,992, which is a continuation of U.S. Ser. No.15/709,746, filed on Sep. 20, 2017, now U.S. Pat. No. 10,129,338, whichis a continuation of U.S. Ser. No. 14/640,364, filed Mar. 6, 2015, nowU.S. Pat. No. 9,800,663. The entire contents of each application isincorporated by reference herein.

TECHNICAL FIELD

This invention relates to wireless communication for dialysis systems.

BACKGROUND

Renal dysfunction or failure and, in particular, end-stage renaldisease, causes the body to lose the ability to remove water andminerals and excrete harmful metabolites, maintain acid-base balance andcontrol electrolyte and mineral concentrations within physiologicalranges. Toxic uremic waste metabolites, including urea, creatinine, anduric acid, accumulate in the body's tissues which can result in aperson's death if the filtration function of the kidney is not replaced.

Dialysis is commonly used to replace kidney function by removing thesewaste toxins and excess water. In one type of dialysistreatment—hemodialysis—toxins are filtered from a patient's bloodexternally in a hemodialysis machine. Blood passes from the patientthrough a dialyzer separated by a semi-permeable membrane from a largevolume of externally-supplied dialysis solution. The waste and toxinsdialyze out of the blood through the semi-permeable membrane into thedialysis solution, which is then typically discarded.

The dialysis solutions or dialysates used during hemodialysis typicallycontain sodium chloride and other electrolytes, such as calcium chlorideor potassium chloride, a buffer substance, such as bicarbonate oracetate, and acid to establish a physiological pH, plus optionally,glucose or another osmotic agent.

SUMMARY

In one aspect, a method includes establishing a wireless connectionbetween a first medical device and a second medical device. Establishingthe wireless connection includes receiving, by the first medical device,via a short-range wireless technology protocol, connection informationrelated to the second medical device. Establishing the wirelessconnection also includes establishing, by the first medical device, awireless connection with the second medical device based on theconnection information.

Implementations can include one or more of the following features.

In some implementations, the wireless connection is established using acommunication protocol other than the short-range wireless technologyprotocol. The connection information specifies information used by thecommunication protocol other than the short-range wireless technologyprotocol.

In some implementations, the method also includes receiving, by aconnection device, from the second medical device, via the short-rangewireless technology protocol, the connection information related to thesecond medical device. The method also includes providing, by theconnection device, to the first medical device, via the short-rangewireless technology protocol, the connection information related to thesecond medical device.

In some implementations, the connection device is a wand.

In some implementations, the connection device is a smartphone.

In some implementations, the method also includes receiving, by thesecond medical device, via the short range wireless technology protocol,connection information related to the first medical device.

In some implementations, the method also includes sending, from thefirst medical device, a request to establish a wireless connection withthe second medical device.

In some implementations, the first medical device and the second medicaldevice are positioned at a sufficient distance relative to each otherfor the first medical device and the second medical device to be closeenough to communicate via the short-range wireless technology protocol.

In some implementations, the first medical device receives theconnection information from the second medical device as a result of thefirst medical device and the second medical device making physicalcontact with each other.

In some implementations, at least one of the first and second medicaldevices includes an accelerometer configured to detect the physicalcontact.

In some implementations, the short-range wireless technology protocol isa Near Field Communication (NFC) protocol. The first medical device andthe second medical device each includes a component configured tocommunicate via NFC.

In some implementations, the component includes an inductor.

In some implementations, the connection information related to thesecond medical device includes a wireless identifier.

In some implementations, the wireless identifier is unique to thedevice.

In some implementations, the first medical device is electricallyisolated from the second medical device.

In some implementations, the first medical device comprises a dialysismachine.

In some implementations, the second medical device comprises anaccessory configured to interact with a dialysis machine.

In some implementations, the second medical device comprises a bloodpressure cuff.

In some implementations, the wireless connection comprises a Bluetoothconnection.

In another aspect, a method includes establishing a wireless connectionbetween a dialysis machine and a dialysis machine accessory.Establishing the wireless connection includes receiving, by the dialysismachine, a wireless identifier associated with the dialysis machineaccessory. The wireless identifier is communicated by a connectiondevice according to a first wireless communication protocol. Thewireless identifier is associated with a second wireless communicationprotocol other than the first wireless communication protocol.Establishing the wireless connection also includes, using the wirelessidentifier associated with the dialysis machine accessory, establishing,by the dialysis machine and the dialysis machine accessory, a wirelessconnection using the second wireless communication protocol. The methodalso includes communicating medical data between the dialysis machineand the dialysis machine accessory using the second wirelesscommunication protocol.

In another aspect, a system includes a medical device. The medicaldevice includes a short-range wireless technology protocol antennaconfigured to receive a wireless identifier related to a medical deviceaccessory via the short-range wireless technology protocol. The medicaldevice also includes an antenna configured to establish a wirelessconnection with the medical device accessory via a communicationprotocol other than the short-range wireless technology protocol usingthe wireless identifier related to the medical device accessory.

Implementations can include one or more of the following advantages.

In some implementations, the methods described can allow a user toeasily pair dialysis machine accessories with dialysis machines. Clinicsthat offer dialysis treatment typically have several dialysis machines,each of which has several dialysis machine accessories. The devices—bothmachines and accessories—can be connected to a wireless network suchthat the accessories can wirelessly communicate with the machines. Foran accessory to communicate with a specific machine, the accessory canbe virtually associated with the machine using the wireless network. Thephysical motion of tapping an accessory against a dialysis machine tovirtually associate the accessory and the dialysis machine can ensurethat the operator can easily select the physical identities ofassociated devices in a physical, visual, and tactile way. The methodsalso improve the efficiency of making virtual associations by reducingthe need to manually enter connection information into dialysis machinesand accessories. Connection information can be easily transmitted usingthe tapping motion described above. The methods described herein canfurther electrically isolate devices from one another by eliminating theneed for communicating electrically sensitive data through electricallines.

The details of one or more embodiments of the invention are set forth inthe accompanying drawings and the description below. Other features,objects, and advantages of the invention will be apparent from thedescription and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a front perspective view of a hemodialysis system.

FIG. 2A is a schematic diagram of a communications system of a deviceused to establish a wireless connection.

FIG. 2B is a schematic diagram of data contained on a memory storageelement of the communications system of FIG. 2A.

FIG. 3A is a schematic diagram of a wireless connection between a hostdevice and an accessory device.

FIG. 3B is a schematic diagram of the wireless connection of FIG. 3Aestablished by a connection device.

FIG. 4A is a network of hemodialysis systems and accessories in aclinic.

FIG. 4B is a block diagram depicting connections within the networkshown in FIG. 4A.

FIG. 4C is a schematic diagram of the network of FIGS. 4A-B with devicesand accessories at various locations within the clinic.

FIG. 5 is a flowchart depicting an example of a process for connecting afirst medical device to a second medical device.

FIGS. 6A-B are flowcharts depicting examples of processes for connectinga first medical device to a second medical device using a connectiondevice.

FIG. 7 is a flowchart depicting an example of establishing a wirelessconnection between a dialysis machine and a dialysis machine accessory.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

Medical devices (e.g., dialysis machines, dialysis machine components,dialysis machine accessories, etc.) can be configured to wirelesslycommunicate with other medical devices through a connection between thedevices. A “connection” established between devices as described hereinrefers to electronic communication between two or more devices such thatdata can be communicated between the devices. The connection can be aunidirectional or a bidirectional connection that allows data to movebetween two nodes in a network. A “node” herein is a member of a networkconnection (e.g., a virtual connection) and represents a correspondingphysical device, such as the devices described above. Basic connectionsbetween devices allows the connected devices to determine the identityof other devices. A connection between devices can have a greater numberof granted permissions than the basic connection described above. Such aconnection is herein referred to as an “association.” For example, in anassociation between devices, a first device can grant the second deviceinput permissions such that the second device can serve as an input forthe first device. In some systems, an operator can manually establishthe wireless association by manually inputting connection information(e.g., a unique wireless identifier) into one or both of the device.However, inputting connection information, which generally includes alengthy and unintuitive sequence of numbers, can be confusing orcumbersome for some operators.

In some examples, two or more medical devices that are part of awireless network, such as a WiFi network, can share connectioninformation with each other using a short-range wireless technologyprotocol, such as Near Field Communication (NFC) or Bluetooth. Forexample, two medical devices that each includes an NFC transceiver(alternatively, e.g., a Bluetooth transceiver) and a wirelesstransceiver can communicate with each other using the transceivers. Themedical devices are equipped with sensor systems and controllers thatcan determine when the operator has performed an action with the medicaldevices that represents an intent to establish a wireless connectionbetween the medical devices. In some implementations, the medicaldevices can be tapped together and/or positioned at a close distancerelative to each other such that the NFC transceivers are withinoperable range of one another. The medical devices can then share theirunique wireless identifiers with one another through the NFC protocol.Once one of the medical devices knows the connection information of theother medical device, a wireless association can be established betweenthe two medical devices.

In some examples, the medical devices require high voltage power cablesthat connect the devices to a central power source. These power cablescan be shielded such that their voltages do not interfere with oneanother. However, as physical data lines utilize low voltages, the powercables can still interfere with the signals carried by the physical datalines. In some examples, the medical devices can communicate informationbetween one another. Physical data lines can be conventionally used, butthe fidelity of communication signals in the physical data lines can beeasily compromised by, for example, the high voltages of the powercables. Thus, medical devices using physical data lines may not beelectrically isolated from one another. The wireless communicationmethods described herein eliminate the need for conventional physicaldata connections, and thus electrically isolate the devices from oneanother.

In some examples, a connection device that includes an NFC transceivercan be used to share connection information of various medical deviceswith other medical devices. For example, the connection device can betapped against and/or positioned at a sufficient distance from a firstmedical device such that the NFC transceiver of the connection devicecan communicate with the NFC transceiver of the first medical device.The connection device can receive the unique wireless identifier of thefirst medical device using the NFC protocol. The connection device canthen be tapped against and/or positioned at a sufficient distance from asecond medical device such that the NFC transceiver of the connectiondevice can provide the unique wireless identifier of the first medicaldevice to the second medical device. Using the wireless identifiers, themedical devices can then establish a wireless connection with eachother. In some implementations, the connection device can receive theunique wireless identifier from each device and directly communicate thewireless identifiers to the wireless network. The wireless network canthen cause a connection to be established between the first and secondmedical devices. In some examples, the connection device is a wand or asmartphone.

FIG. 1 shows a hemodialysis system 100 configured to wirelesslycommunicate with other medical devices. The hemodialysis system 100includes a hemodialysis machine 102 connected to a disposable bloodcomponent set 104 that partially forms a blood circuit. The operator canmanage and control treatment parameters of the hemodialysis system 100using an external wireless keyboard 101. During hemodialysis treatment,an operator connects arterial and venous patient lines 106, 108 of theblood component set 104 to a patient. The blood component set 104includes an air release device 112, which contains a self-sealing ventassembly that allows air but does not allow liquid to pass. As a result,if blood passing through the blood circuit during treatment containsair, the air release device 112 will vent the air to atmosphere.

The blood component set 104 is secured to a module 130 attached to thefront of the hemodialysis machine 102. The module 130 includes the bloodpump 132 capable of circulating blood through the blood circuit. Themodule 130 also includes various other instruments capable of monitoringthe blood flowing through the blood circuit. The module 130 includes adoor that when closed, as shown in FIG. 1 , cooperates with the frontface of the module 130 to form a compartment sized and shaped to receivethe blood component set 104. In the closed position, the door pressescertain blood components of the blood component set 104 againstcorresponding instruments exposed on the front face of the module 130.

The operator uses a blood pump module 134 to operate the blood pump 132.The blood pump module 134 includes a display window, a start/stop key,an up key, a down key, a level adjust key, and an arterial pressureport. The display window displays the blood flow rate setting duringblood pump operation. The start/stop key starts and stops the blood pump132. The up and down keys increase and decrease the speed of the bloodpump 132. The level adjust key raises a level of fluid in an arterialdrip chamber.

The hemodialysis machine 102 further includes a dialysate circuit formedby the dialyzer 110 various other dialysate components and dialysatelines connected to the hemodialysis machine 102. Many of these dialysatecomponents and dialysate lines are inside the housing 103 of thehemodialysis machine 102 and are thus not visible in FIG. 1 . Duringtreatment, while the blood pump 132 circulates blood through the bloodcircuit, dialysate pumps (not shown) circulate dialysate through thedialysate circuit.

A dialysate container 124 is connected to the hemodialysis machine 102via a dialysate supply line 126. A drain line 128 and an ultrafiltrationline 129 also extend from the hemodialysis machine 102. The dialysatesupply line 126, the drain line 128, and the ultrafiltration line 129are fluidly connected to the various dialysate components and dialysatelines inside the housing 103 of the hemodialysis machine 102 that formpart of the dialysate circuit. During hemodialysis, the dialysate supplyline 126 carries fresh dialysate from the dialysate container 124 to theportion of the dialysate circuit located inside the hemodialysis machine102. As noted above, the fresh dialysate is circulated through variousdialysate lines and dialysate components, including the dialyzer 110,that form the dialysate circuit. As will be described below, as thedialysate passes through the dialyzer 110, it collects toxins from thepatient's blood. The resulting spent dialysate is carried from thedialysate circuit to a drain via the drain line 128. Whenultrafiltration is performed during treatment, a combination of spentdialysate (described below) and excess fluid drawn from the patient iscarried to the drain via the ultrafiltration line 129.

The dialyzer 110 serves as a filter for the patient's blood. Thedialysate passes through the dialyzer 110 along with the blood, asdescribed above. A semi-permeable structure (e.g., a semi-permeablemembrane and/or semi-permeable microtubes) within the dialyzer 110separates blood and dialysate passing through the dialyzer 110. Thisarrangement allows the dialysate to collect toxins from the patient'sblood. The filtered blood exiting the dialyzer 110 is returned to thepatient. The dialysate exiting the dialyzer 110 includes toxins removedfrom the blood and is commonly referred to as “spent dialysate.” Thespent dialysate is routed from the dialyzer 110 to a drain.

A drug pump 192 also extends from the front of the hemodialysis machine102. The drug pump 192 is a syringe pump that includes a clampingmechanism configured to retain a syringe 178 of the blood component set104. The drug pump 192 also includes a stepper motor configured to movethe plunger of the syringe 178 along the axis of the syringe 178. Ashaft of the stepper motor is secured to the plunger in a manner suchthat when the stepper motor is operated in a first direction, the shaftforces the plunger into the syringe, and when operated in a seconddirection, the shaft pulls the plunger out of the syringe 178. The drugpump 192 can thus be used to inject a liquid drug (e.g., heparin) fromthe syringe 178 into the blood circuit via a drug delivery line 174during use, or to draw liquid from the blood circuit into the syringe178 via the drug delivery line 174 during use.

The hemodialysis machine 102 includes a user interface with inputdevices such as a touch screen 118 and a control panel 120. The touchscreen 118 and the control panel 120 allow the operator to input variousdifferent treatment parameters to the hemodialysis machine 102 and tootherwise control the hemodialysis machine 102. The touch screen 118displays information to the operator of the hemodialysis system 100. Thetouch screen 118 can also indicate whether a peripheral or accessorydevice, such as the keyboard 101, is connected to the hemodialysismachine 102. The keyboard 101 is a wireless keyboard that connects tothe hemodialysis machine 102 by communicating directly or indirectlywith a communication system 107 in the dialysis machine 102. Duringtreatment, the keyboard 101 and other peripheral devices can be used tocontrol, monitor, and determine treatment parameters and variables.

FIG. 2A is a block diagram of a communications system 201 of a device200 that can be used to establish a wireless association between twodevices. The device 200 can itself be one of the devices connected bythe wireless association. The wireless association can be formed using awireless protocol such as, for example, WPA, WPA2, or WEP, among others.Alternatively, the device can facilitate the establishment of thewireless association between two other devices. The device 200 can be ahost device (e.g., the hemodialysis machine 102), a peripheral device(e.g., the wireless keyboard 101 of FIG. 1 ), or a connection device(the function of which is described in more detail below).

A controller 307 of the device 200 accesses and controls thecommunications system 201, which includes a wireless transceiver 303, anNFC transceiver 305, a user interface 308, and a memory storage element309. The wireless transceiver 303 is an antenna that connects the device200 to a wireless network (not shown) to transmit and receive data usingwireless connections. The NFC transceiver 305 of the device 200 is anantenna that transmits and receives data using NFC connections. In someexamples, the antenna forms or includes an inductor such that when twoNFC transceivers are placed within range of one another, they form atransformer that generates an electromagnetic force inverselyproportional to the distance between the transceivers. The controller307 manages transmission and receipt of data in the communicationssystem 201 and also stores data received from the wireless transceiverand/or the NFC transceiver 305 on the memory storage elements 309. Thecontroller 307 further retrieves data from the memory storage element309 to transmit using the wireless transceiver 303 and/or the NFCtransceiver 305. The controller 307 executes subroutines (which will bedescribed in more detail below) stored on the memory storage element309. The user interface 308 displays communications-related informationand/or allows the operator to input data. For example, the userinterface 308 can show the devices with which the device 200 haswireless associations and/or devices that have granted input permissionsto the device 200. The operator can further use the user interface 308to accept connection requests or to set default settings for thesubroutines 330, which will be described below. In this example, thedevice 200 includes a sensor system 315. The sensor system 315 on thedevice 200 includes, for example, accelerometers for collectinginformation related to a motion of the device.

FIG. 2B schematically shows examples of data stored on an example memorystorage element 309 of the device 200. The memory storage element 309can store connection information 321 that classifies the device 200 anduniquely identifies the device 200. The connection information 321includes an identifier 317 and a label 319. The identifier 317represents the unique identity of the device on the wireless network,such as, for example, a WiFi network. The label 319 determines the typeor class of the device. The label can be HOST, PERIPHERAL, or CONNECTOR.As will be described below, the identifier 317 can be used to determinethe devices connected using the wireless protocol, and the labels can beused to determine characteristics of the connection.

The memory storage element 309 further contains subroutines 330 that canbe executed by the controller 307 to establish a wireless association(e.g., the wireless association 310 of FIG. 3A-B, which will bedescribed below). These subroutines 330 include a Tap-to-AssociateSubroutine 311, Discover Subroutine 312, a Pairing Subroutine 313, andan Association Subroutine 314.

The Tap-to-Associate Subroutine 311 allows a user to pair and associatedevices by tapping the device 200 against a second device that is alsoexecuting a Tap-to-Associate Subroutine 311. The default settings of thedevice 200 are set such that the Tap-to-Associate Subroutine 311 isautomatically executing by default. In this example, when the controller307 is executing the Tap-to-Associate Subroutine 311, the controller 307can receive information related to a motion of the device from thesensor system 315. The Tap-to-Associate Subroutine 311 can cause thecontroller 307 to continuously receive the motion information until themotion exceeds a threshold value. When the motion exceeds the thresholdvalue, the Tap-to-Associate Subroutine 311 can sequentially execute theDiscover Subroutine 312 and the Pairing Subroutine 313.

The Discover Subroutine 312 enables functions of the NFC transceiver 305so that the device 200 can communicate with other devices having enabledNFC transceivers. In particular, the controller 307 executes theDiscover Subroutine 312 to place the NFC transceiver 305 in a virtuallydiscoverable state such that other nearby NFC transceivers can detect(or discover) the NFC transceiver 305 of the device 200. (A device withan NFC transceiver in a discoverable state is hereby also called a“discoverable device.”) The NFC transceiver 305 of the discoverabledevice 200 can listen for other discoverable devices by creating, forexample, an NFC server socket. The Discover Routine 312 is initializedafter the Tap-to-Associate Subroutine 311 is triggered, as describedabove.

The Pairing Subroutine 313 can connect two devices using the NFCtransceivers so that the devices can share connection information withone another. In particular, after the Discover Subroutine 312 and theNFC transceiver 305 has discovered a second device, the controller canexecute the Pairing Subroutine 313 to use the NFC transceiver 305 topair with the second device. The second device selected by the PairingSubroutine 313 is, for example, a discoverable device in closestproximity to the device 200. Upon initiating a pairing with the seconddevice, the NFC server socket can return an NFC socket for the seconddevice, thus forming an NFC connection to pair the device 200 with thesecond device. Using the NFC connection, the device 200 retrieves andstores the identifier and the label of the second device. The PairingSubroutine also causes the device 200 to send its own identifier 317 andlabel 319 to the second device using the NFC connection.

The Association Subroutine 314 forms the wireless association anddetermines the characteristics of the wireless association. Aftercompleting the Pairing Subroutine 313, the device 200 initiates theAssociation Subroutine 314. The Association Subroutine uses theidentifiers 317 and labels 319 for the two devices to form the wirelessassociation between the two devices. The identifiers determine the twonodes that the wireless association connects, and the labels determinethe type of wireless association between the nodes. The identifierretrieved from the Pairing Subroutine 313 is used to determine one oftwo nodes.

The identifier that the Association Subroutine 314 uses to determine thesecond node depends on the label 319 of the device 200. If the device200 has a HOST or PERIPHERAL label, the Association Subroutine 314 usesthe device's own identifier 317 to define the second node. The type ofwireless association formed then depends on the label of the seconddevice and the label of the device 200. An example of such animplementation will be described below with respect to FIG. 3A.

If the device 200 has a CONNECTOR label, the device 200 does not use itsown identifier 317 as the second node. Instead, the operator pairs thedevice 200 (e.g., via the Tap-to-Associate Subroutine 311) with a thirddevice to retrieve an identifier for the second node. The label of thesecond device and the label of the third device determine the type ofwireless association formed between the two devices. An example of suchan implementation will be described below with respect to FIG. 3B.

As a result of the two conditions described above for the inputs of theAssociation Subroutine, the Association Subroutine 314 forms wirelessassociations between devices with PERIPHERAL or HOST labels. Inaddition, one of the devices can be the device 200. When one device is aPERIPHERAL device and the other device is a HOST device, the two devicesform an association such that, for example, the HOST device grantspermission to the PERIPHERAL device to serve as an input device for theHOST device. The PERIPHERAL device thus can control functions of theHOST device and/or can deliver data to the HOST device. When twoPERIPHERAL devices or two HOST devices are connected using theAssociation Subroutine 314, the Association Subroutine 314 may promptthe operator to indicate which device serves as an input device andwhich device serves as an input receiving device.

Methods of Use

FIGS. 3A-B depict an example of a wireless association 310 establishedbetween a host device 201 and a peripheral device 202. In this example,the host device 201 is a hemodialysis machine, and the peripheral device202 is a keyboard. Referring to FIG. 3A, the host device 201 and theperipheral device 202 are paired directly to form the wirelessassociation 310. Referring to FIG. 3B, the connection device 203 helpsto establish the wireless association 310 between the host device 201and the peripheral device 202. The wireless association 310 can allowthe peripheral device 202 to controls treatment parameters through datainputted through the peripheral device 202. The operator can modifytreatment parameters set on the host device 201 by entering treatmentinstructions into the peripheral device 202 which are sent to the hostdevice 201 through the wireless association 310.

The wireless association can be established using the following methods:(i) the host device 201 and the peripheral device 202 directly pair withone another to form the wireless association (as shown in FIG. 3A), or(ii) a connection device 203 communicates with each of the host device201 and the peripheral device 202 and then causes the wirelessassociation 310 to be established between the host device 201 and theperipheral device 202 (as shown in FIG. 3B). Both of these methods willbe described in detail below. The devices 201, 202, 203 include thecommunications systems as described with respect to FIGS. 2A-B.Referring to FIG. 3A, the host device 201 having a HOST label 319 a anda unique identifier 317 a and the peripheral device 202 having aPERIPHERAL label 319 b and a unique identifier 317 b are paired directlyto form the wireless association 310. In FIG. 3B, the connection device203 having CONNECTOR label 319 c and a unique identifier 317 c helps toestablish the wireless association 310 between the host device 201 andthe peripheral device 202. The connection device 203 can be a wand thatincludes the aspects as described above for the connection device.

FIG. 3A shows an example of associating the host device 201 with theperipheral device 202 to form the wireless association 310. The operatordirectly pairs the host device 201 with the peripheral device 202 usingan NFC connection 304.

The operator brings the peripheral device 202 within a close proximityof the host device 201 (e.g., within the NFC range of the NFCtransceiver of the host device 201). In some implementations, theperipheral device 202 can be tapped against the host device 201. Thetapping gesture can generate a particular motion signature of theperipheral device 202 that triggers the Tap-to-Associate Subroutine 311of the peripheral device 202. The tapping gesture can also generate aparticular motion signature of the host device 201 that can trigger theTap-to-Associate Subroutine 311 of the host device 201. As a result, thehost device 201 and peripheral device 202 can initiate their respectiveDiscover Subroutines 312 and can be placed in discoverable states.

The Pairing Subroutine 313 can then be initiated, causing the peripheraldevice 202 to pair with a device with a discoverable NFC transceiver. Insome implementations, such as when there are multiple devices indiscoverable states, the peripheral device 202 may pair with the devicethat is in closest proximity to the peripheral device 202. The devices201, 202 are typically physically close to one another when the operatortaps the peripheral device 202 against the host device 201. As a result,the peripheral device 202 can pair with the host device 201.

Once the NFC connection 304 is established, the peripheral device 202can then retrieve the HOST label 319 a and the identifier 317 a of thehost device 201 through the NFC connection 304. The peripheral device202 can also send the PERIPHERAL label 319 b and the identifier 317 b ofthe peripheral device 202 to the host device 201 using the NFCconnection 304.

After the Pairing Subroutine is complete, the peripheral device 202 canthen initiate the Association Subroutine 314 to determine the type ofwireless association formed and the nodes connected by the wirelessassociation. In some implementations, the Association Subroutine 314identifies the identifier 317 a stored on the peripheral device 202 asthe first of two nodes of the wireless association. The AssociationSubroutine 314 can further identify the identifier 317 b— the identifierof the peripheral device 202—as the second node of the wirelessassociation. The identifier 317 b is associated with the PERIPHERALlabel 319 b, and the identifier 317 a is associated with the HOST label319 a. As a result, the Association Subroutine 314 can set theperipheral device 202 to be an input device for the host device 201. Inother words, the Association Subroutine 314 can instruct the host device201 to grant input permissions to the peripheral device 202, thusforming the wireless association 310.

FIG. 3B shows an example of associating the host device 201 with theperipheral device 202 to form the wireless association 310 using theconnection device 203. The connection device 203 can be used toestablish a wireless association between two devices. Generally, theconnection device 203 can establish a wireless association between adevice with a HOST label (e.g., the host device 201) and a device with aPERIPHERAL label (e.g., the peripheral device 202). The connectiondevice 203 includes a control screen 207 (e.g., the user interface ofFIG. 2A) that the operator uses to manage the connections of theconnection device 203 (e.g., NFC, USB, or WiFi connections) andsubsequent wireless associations established by the connection device203 (e.g., the wireless association 310).

By way of general overview, in the example described below with respectto FIG. 3B, the operator first pairs the host device 201 with theconnection device 203 to form the NFC connection 304 a. The operatorthen pairs the peripheral device 202 with the connector device 203 toform the NFC connection 304 b. Labels 317 a, 317 b and identifiers 319a, 317 b, which are transferred and stored through the two pairings,allow the connection device 203 to cause the wireless association 310 tobe formed between the host device 201 and the peripheral device 202.Details of each of these steps will be described in detail below. Thewireless association 310 can be formed by, for example, a central serverof the wireless network or by the connection device 203.

The operator can form the NFC connection 304 a by bringing theconnection device 203 within a close proximity of the host device 201(e.g., within the NFC range of the NFC transceiver of the host device201) and tapping the connection device 203 against the host device 201.The tapping motion can trigger the Tap-to-Associate Subroutines of theconnection device 203 and the host device 201 and can place them indiscoverable states. The Tap-to-Associate Subroutine can further causethe connection device 203 to initialize the Pairing Subroutine, whichcan instruct the connection device 203 to pair with the physicallyclosest device with a discoverable NFC transceiver. As the operatortapped the connection device 203 against the host device 201 to run theTap-to-Associate Subroutine, the devices 201, 203 are physically closestto one another as well. As a result, the connection device 203 can pairwith the host device 201. As a result, the NFC connection 304 a pairsthe connection device 203 and the host device 201. The connection device203 then can retrieve the HOST label 319 a and the identifier 317 a ofthe host device 201 using the NFC connection 304 a. The connectiondevice 203 also can send the CONNECTOR label 319 c and the identifier317 c to the host device 201 using the NFC connection 304 a.

After the Pairing Subroutine is complete, the connection device 203 caninitiate the Association Subroutine 314. As the label 319 c of theconnection device 303 is CONNECTOR, the Association Subroutine 314 caninstruct the operator to pair the connection device to another device tocomplete the wireless association.

The operator can form the NFC connection 304 a by bringing theconnection device 203 within a close proximity of the peripheral device202 (e.g., within the NFC range of the NFC transceiver of the peripheraldevice 202) and tapping the connection device 203 against the peripheraldevice 202. The tapping motion can trigger the Tap-to-AssociateSubroutines of the connection device 203 and the peripheral device 202and places them in discoverable states. The Tap-to-Associate Subroutinefurther can cause the connection device 203 to initialize the PairingSubroutine, which can instruct the connection device 203 to pair withthe physically closest device with a discoverable NFC transceiver. Asthe operator tapped the connection device 203 against the peripheraldevice 202 to run the Tap-to-Associate Subroutine, the devices 202, 203are physically closest to one another as well. As a result, theconnection device 203 pairs with the host device 201. As a result, theNFC connection 304 b pairs the connection device 203 and the peripheraldevice 202. The connection device 203 then can retrieve the PERIPHERALlabel 319 b and the identifier 317 b of the peripheral device 202 usingthe NFC connection 304 b. The connection device 203 also can send theCONNECTOR label 319 c and the identifier 317 c to the peripheral device202 using the NFC connection 304 b.

After the second iteration of the Pairing Subroutine is complete, theconnection device 203 can initiate the Association Subroutine 314 todetermine the nodes connected by the wireless association and the typeof wireless association formed. As the label 319 c of the connectiondevice 203 is CONNECTOR, the Association Subroutine 314 can identify theidentifiers 317 a, 317 b stored on the connection device 203 as thenodes of the wireless association 310. The identifier 317 b isassociated with the PERIPHERAL label 319 b, and the identifier 317 a isassociated with the HOST label 319 a. As a result, the AssociationSubroutine 314 can set the peripheral device 202 to be an input devicefor the host device 201. In other words, the Association Subroutine 314can form the wireless association 310 such that the host device 201grants input permissions to the peripheral device 202.

Still referring to FIG. 3B, while the connection device 203 has beendescribed above to implement the Association Subroutine 314 to form thewireless association 310 between the host device 201 and the peripheraldevice 202, in some implementations, the host device 201 can implementthe Association Subroutine 314. For example, using NFC connections, theconnection device 203 can retrieve the connection information of theperipheral device 202 using the Pairing Subroutine. Without proceedingto the Association Subroutine 314, the connection device 203 uses thePairing Subroutine again. During the second iteration of the PairingSubroutine, the connection device 203 delivers the connectioninformation of the peripheral device 202 to the host device 201 so thatthe host device 201 can initiate the Association Subroutine 314 to formthe wireless association between the host device 201 and the peripheraldevice 202. As a result, the connection device 203 does not perform thesubroutine to establish the wireless association but rather deliversinformation such that the host device 201 can establish the wirelessassociation. In other implementations, a server of the wireless networkcan implement the Association Subroutine.

FIGS. 4A-C depict an example network of hemodialysis machines andaccessory devices situated, e.g., in a clinic. The network containsseveral connected machines and accessories at various physical locationsthroughout the clinic. FIG. 4A schematically depicts the wirelessnetwork 360 connecting the hemodialysis machines and accessory devices.FIG. 4B schematically depicts the wireless associations and NFCconnections between the devices. FIG. 4C schematically represents thephysical locations of the devices throughout the clinic.

Referring to FIG. 4A, various devices including hemodialysis machines102 a-c, a smartphone 352, the connection device 203, keyboards 101 a-d,and blood pressure cuffs 350 a-b are connected to the wireless network360. Each connected device has an identifier (e.g., a unique InternetProtocol address) that distinguishes the device on the wireless network360 from other devices. Each connected device further has a label (e.g.,HOST, PERIPHERAL, CONNECTOR) that reflects its use in the clinic. Thehemodialysis machines 102 a-c have HOST labels, the connection device203 have CONNECTOR label, and the keyboards 101 a-d and the bloodpressure cuffs 350 a-b have PERIPHERAL labels. The smartphone 352 may belabeled as either PERIPHERAL or CONNECTOR. For example, in some cases,the smartphone 352 can be used as an input device similar to thekeyboards 101 a-d and thus has a PERIPHERAL label. In other cases, thesmartphone 352 can be used as a connection device similar to theconnection device 203 and thus has a CONNECTOR label. In the examplerepresented in FIGS. 4A-C, the smartphone 352 has a PERIPHERAL label.The devices have basic wireless connections with one another. Thedevices can thus determine the identifiers and the labels of each otherdevice connected to the wireless network 360.

FIG. 4B shows a node diagram of the connections between the devices ofFIG. 4A. FIG. 4B shows wireless associations 365 a-i in the network,which are represented by dashed lines, and NFC connections 370 a-b,which are represented by solid lines. The wireless associations 365 a-irepresent associations over the wireless network 360 of FIG. 4A. Theseassociations or connections have been formed using the NFC-facilitatedTap-to-Associate methods described above with respect to FIGS. 2-3 .

The hemodialysis machine 102 a has formed respective wirelessassociations 365 a-c with the smartphone 352, the blood pressure cuff350 a, and the keyboard 101 a. As the hemodialysis machine 102 a has aHOST label, the smartphone 352, the cuff 350 a, and the keyboard 101 aserve as input devices for the hemodialysis machine 102 a. The bloodpressure cuff 350 a, which an operator can use to detect the bloodpressure of a patient, delivers blood pressure measurements to thehemodialysis machine 102 a. The hemodialysis machine 102 a can displaythe blood pressure measurements to the operator (e.g., on the touchscreen 118) or can activate an alarm if the blood pressure measurementsdecreases or increases beyond a threshold blood pressure. As describedabove, the operator can change treatment parameters of the hemodialysismachine 102 a using touch screen 118 and the control panel 120. Theoperator can also use the keyboard 101 a to control the treatmentparameters of the hemodialysis machine 102 a. For example, the operatortypes numbers into the keyboard 101 a, and the touch screen of thehemodialysis 102 a will display the input from the keyboard 101 a. Theoperator can change parameters such as flow rate or issue stop and startcommands using the keyboard 101 a. The hemodialysis machine 102 has alsogranted input permissions to the smartphone 352 such that the operatorcan use the smartphone 352 to issue commands to the hemodialysis machine102 a.

The blood pressure cuff 350 a is further connected to the keyboard 101 busing the wireless association 365 d. As the blood pressure cuff 350 aand the keyboard 101 b are both PERIPHERAL devices, the operator selectswhich device serves as the input device for the other device (e.g.,using a connection device as described above). In this example, theoperator has chosen the keyboard 101 b to serve as an input device forthe blood pressure cuff 350 a. As a result, the keyboard 101 b controlsoperations of the blood pressure cuff 350 a. The operator can use thekeyboard 101 b to start or stop the blood pressure cuff 350 a orinstruct the blood pressure cuff to perform other functions (e.g., senddata to another device, sense pressure periodically every 10 minutes,etc.).

The smartphone 352 has the wireless association 365 e with thehemodialysis machine 102 b in addition to the wireless association 365 awith the hemodialysis machine 102 a. As a result, the smartphone 352 canserve as an input device for both machines 102 a-b. The operator can usethe smartphone 352 to control both machines 102 a-b simultaneously. Forexample, in a case where both machine 102 a-b need to be stoppedsimultaneously (due to, e.g., an earthquake or an attack or anotheremergency situation), the operator can stop both machines using thesmartphone 352 associated with both machines 102 a-b. The smartphone 352can also be used to control each machine 102 a-b individually. Theoperator can toggle between using the user interface (e.g., a touchscreen of the smartphone) to control the hemodialysis machine 102 a andusing the user interface, which can include the touch screen 118 and thecontrol panel 120 of the hemodialysis machine 102 a, to control thehemodialysis machine 102 b. A user application can be loaded onto thesmartphone 352 to facilitate the functions described above.

The hemodialysis machine 102 b also has the wireless association 365 fwith the blood pressure cuff 350 b (with a similar function as thewireless association 365 b between the blood pressure cuff 350 a and thehemodialysis machine 102 a) and the wireless association 365 g with thekeyboard 101 c. The keyboard 101 c has two wireless associations: thewireless association 365 g and the wireless association 365 h. Thekeyboard 101 c serves as an input device for both the hemodialysismachine 102 b and the blood pressure cuff 350 b. The operator can, insome examples, switch between delivering commands to the hemodialysismachine 102 b and the blood pressure cuff 350 b by pressing a switch keyon the keyboard 101 b.

The wireless association 365 i connects the hemodialysis machine 102 cto the keyboard 101 d, which serves as an input device for thehemodialysis machine 102 c. The hemodialysis machine 102 c has furtherformed the NFC connection 370 b with the connection device 203. Theconnection device 203 can be used to form two NFC connections: the NFCconnection 370 a with the smartphone 352 and the NFC connection 370 bwith the hemodialysis machine 102 c. As a result, the connection device203 has the identifiers and labels for the smartphone 352 and thehemodialysis machine 102. The connection device 203 can be prepared toform a wireless association between the smartphone 352 and thehemodialysis machine 102 c so that the smartphone 352 can have awireless association with all of the hemodialysis machines 102 a-clocated in the example clinic.

FIG. 4C schematically represents the physical locations of the devicesin the clinic described in FIGS. 4A-B. A wireless router 382 creates thewireless network 360 of FIG. 4A, which has a wireless coverage region381. The wireless coverage region 381 is represented by a circlecentered at the position of the wireless router 382 with a radius of awireless range 385. Devices within the wireless coverage region 381 canform basic wireless connections with other devices within the wirelessrange 381.

Each device has an NFC transceiver and therefore forms an NFC coverageregion. In FIG. 4C, the NFC coverage region 390 around the hemodialysismachine 102 a is shown, though it should be understood that theremaining devices also form NFC coverage regions. The NFC coverageregion 390 is defined by a circle centered at the position of thehemodialysis machine 102 a with a radius of an NFC range 395. Deviceswithin the NFC coverage region 390 generally can detect a strong enoughsignal from the NFC transmitter of the hemodialysis machine 102 a toform an NFC connection with the hemodialysis machine 102 a. As shown inFIG. 4C, the keyboard 101 a is outside of the NFC coverage region 390.Referring briefly back to FIG. 4B, the keyboard 101 a has formed thewireless association 365 c with the hemodialysis machine 102 a, so, eventhough the keyboard 101 a is outside of the NFC coverage region 390, thekeyboard 101 a can still be used to control the hemodialysis machine 102a. Once the wireless association 365 c is formed, the operator can movethe keyboard 101 a outside of the NFC coverage region 390 of thehemodialysis machine 102 a and the wireless association 365 c willremain intact as both the hemodialysis machine 102 a and the keyboard101 a are still both within the wireless coverage region 381.

The blood pressure cuff 350 a and the keyboard 101 b are both within theNFC coverage region 390 and therefore both can form an NFC connectionwith the blood hemodialysis machine 102 a. The blood pressure cuff 350 ais located a distance D₁ from the hemodialysis machine 102 a, and thekeyboard 101 b is located a distance D₂ from the keyboard 101 b. The NFCsignal strength decreases proportional to the inverse square of thedistance from the source. As the distance D₂ is greater than thedistance D₁, the NFC signal from the blood pressure cuff 350 a isstronger than the NFC signal from the keyboard 101 b. The hemodialysismachine 102 a can thus determine that the blood pressure cuff 350 a iscloser than the keyboard 101 b. As a result, if the operator triggersthe Tap-to-Associate Subroutines of the blood pressure cuff 350 a andthe hemodialysis machine 102 a, the blood pressure cuff 350 a can form awireless association (e.g., the wireless association 365 b of FIG. 4B)with the hemodialysis machine 102 a.

Generally, an operator establishes the connection between the first andthe second medical devices such that the operator can use the secondmedical device to, for example, control operations or provide data tothe first medical device. The first medical device can be, for example,a hemodialysis machine. The second medical device can be, for example, awireless keyboard. The first medical device, the second medical device,and the connection device are equipped with first transceivers toconnect to a first network that connects medical devices to one anotherusing a first communication protocol (e.g., NFC). The first medicaldevice, the second medical device, and the connection device are furtherequipped with second transceivers that connect to a second network thatconnects medical devices to one another using a second communicationprotocol (e.g., WPA, WPA2, WEP, etc.).

FIG. 5 is a flowchart 500 of establishing a wireless connection betweena first medical device and a second medical. At step S510, via ashort-range wireless technology protocol, connection information relatedto the second medical device is received. The connection information canbe received by the first medical device. In some examples, theshort-range wireless technology protocol is an NFC protocol. In someexamples, the first medical device is a hemodialysis machine, and thesecond medical device is a wireless keyboard configured to interact withthe hemodialysis machine. In some examples, the first medical devicefirst receives, via the short-range wireless technology protocol, arequest to establish a wireless connection using a communicationprotocol other than the short-range wireless technology protocol. Thewireless connection can be between the first medical device and thesecond medical device. The connection information can specifyinformation used by the communication protocol other than theshort-range wireless technology protocol. Prior to receiving therequest, the first medical device can be placed in a discoverable statesuch that the second medical device detects the first medical deviceusing the short-range wireless technology protocol. The second medicaldevice can also be placed in a discoverable state such that the firstmedical device detects the second medical device using the short-rangewireless technology protocol. The first and second medical devices cancontain the subroutines as described above with respect to FIG. 2B. As aresult, the first and second medical devices can be placed indiscoverable states by triggering the Tap-to-Associate Subroutines. Upontriggering the Tap-to-Associate Subroutines, the second medical devicecan also send the request to establish the wireless connection to thefirst medical device. One or both medical devices can be mobile suchthat the operator can move one or both medical devices withincommunication range using the first communication protocol. The operatorcan instruct the first medical device to accept the request, and thenthe first medical device receives the connection information related tothe second medical device using the short-range wireless technologyprotocol. The first medical device can also send, via the short-rangewireless technology protocol, connection information related to thefirst medical device to the second medical device. The connectioninformation for each device can include an identifier and a label of thedevice. The transfer of connection information between the first andsecond medical devices can occur as part of the Pairing Subroutinedescribed with respect to FIG. 2B.

At step S520, the wireless connection is established between the firstmedical device and the second medical device. In some examples, thefirst medical devices establishes the wireless connection. Referringback to the Association Subroutine described with respect to FIG. 2B,the first medical device can use the unique identifier of the firstmedical device and the unique identifier of the second medical device asthe nodes of the wireless network. The labels of the first and secondmedical devices can determine the type of wireless connectionestablished between the first and second medical devices. From the abovesteps, it should be understood the connection information associatedwith the communication protocol can be transmitted via the short-rangewireless technology protocol. The connection information can then beused to establish the permanent wireless connection using thecommunication protocol.

FIGS. 6A-6B are flowcharts 600A-B of establishing a connection, such asthe wireless associations described above, between a first medicaldevice and a second medical using a connection device. In the flowchart600A of FIG. 6A, a connection device establishes the wireless connectionbetween the first and second medical device.

At step S610A, the connection device receives, via a first communicationprotocol, connection information related to a first medical device. Insome examples, the first communication protocol is an NFC protocol. Insome examples, the first medical device is a hemodialysis machine, thesecond medical device is a wireless keyboard configured to interact withthe hemodialysis machine, and the connection device is a smartphone or awand.

At step S620A, the connection device receives, via the firstcommunication protocol, connection information related to a secondmedical device. The operator can trigger the Tap-to-Associate Subroutineon the connection device with each of the first and second medicaldevices. As a result, the connection device can execute the PairingSubroutine and can receive connection information from both the firstmedical device and the second medical device.

At step S630A, the connection device establishes a connection on asecond communication protocol between the first medical device and thesecond medical device. The connection device implements the AssociationSubroutine, which uses the connection information received in stepsS610A and S620A to establish the connection between the first and secondmedical devices and determine the type of connection formed between thefirst and second medical devices. In some examples, the secondcommunication protocol is a wireless protocol such as WEP, WPA, or WPA2.

The flowchart 600B of FIG. 6B depicts an alternative implementation ofestablishing a wireless connection between the first and second medicaldevice using the connection device. A connection device providesconnection information of the first medical device to establish awireless connection between, for example, the first medical device andthe second medical device.

At step S610B, the connection device receives, via a communicationprotocol, connection information related to the first medical device.The connection device can execute a first iteration of the PairingSubroutine and receives connection information from the medical device.

At step S620B, the connection device provides, via the communicationprotocol, the connection information. The connection device can providethe connection information to the second medical device to establish thewireless connection. The connection device can also provide theconnection information to a server of a wireless network through whichthe wireless connection is formed. The connection device can execute asecond iteration of the Pairing Subroutine and sends the previouslyreceived connection information to the second medical device. The secondmedical device can then implement the Association Subroutine toestablish the wireless connection between the first medical device andthe second medical device.

FIG. 7 is a flowchart 700 of establishing a wireless connection betweena dialysis machine and a dialysis machine accessory.

At step S710, a wireless identifier associated with the dialysis machineaccessory is received. In some examples, the dialysis machine receivesthe wireless identifier. The wireless identifier can be communicated bya connection device according to a first wireless communicationprotocol. The wireless identifier can be associated with a secondwireless communication protocol other than the first wirelesscommunication protocol. In some examples, the first wirelesscommunication protocol is an NFC protocol and the second wirelesscommunication protocol is WPA, WPA2, or WEP.

At step S720, a wireless connection is established using the wirelessidentifier associated with the dialysis machine accessory. In someexamples, the dialysis machine establishes the wireless connection. Inother examples, the dialysis machine accessory establishes the wirelessconnection. The wireless connection can be established using the secondwireless communication protocol.

At step S730, the dialysis machine accessory can be communicated with.In some examples, the dialysis machine communicates with the dialysismachine accessory; in some examples, the dialysis machine accessorycommunicates with the dialysis machine; and in other examples, two-waycommunication occurs between the dialysis machine and the dialysismachine accessory. Medical data can be communicated between the dialysismachine and the dialysis machine accessory using, for example, thewireless connection.

While certain implementations have been described, other implementationsare possible.

In the block diagram of FIG. 2A depicting an example communicationssystem 201 of a device 200, the communications system 201 is describedto include a wireless transceiver 303, an NFC transceiver 305, a userinterface 308, a memory storage element 309, and a sensor system 315. Inalternative implementations, the device does not include one or more ofa wireless transceiver, an NFC transceiver, a user interface, a memorystorage element, and a sensor system. For example, in someimplementations, the device does not have a user interface but can stillbe used with the subroutines and methods described in this application.In other examples, the device does not have both a wireless transceiverand an NFC transceiver. The device can include just a wirelesstransceiver and use the wireless transceiver to pair with other devicesand to form a wireless association with other devices. The sensor systemis an optional system within the communications system.

While FIG. 2A depicts the device 200 to have an identifier and a label,in some implementations, the device can have only an identifier. In suchimplementations, when an association been formed between two devices, anoperator can indicate on a user interface of either device which deviceserves as a host device and which serves as a peripheral device.

While the communication systems 201 of the device 200 of FIG. 2A hasbeen described as a generic communications system for devices herein(e.g., a hemodialysis machine, a keyboard, a connection device, a bloodpressure cuff, etc.), in some implementations, the communications systemof a device only includes a subset of the sub-systems and hardwaredescribed. Some devices may only include a subset of the subroutinesdescribed. For instance, in some implementations, only devices with theHOST label have the Association Subroutine. As a result, connectioninformation is delivered only to the devices with HOST labels, and thehost devices accordingly form the wireless associations between devices.Connection devices and peripheral devices assist in deliveringinformation to the host devices.

While the label 319 of the device 200 has been described to be one ofHOST, PERIPHERAL, or CONNECTOR, in some implementations, additionallabels can be used to further classify a device. For example, thePERIPHERAL label can include sub-labels, such as INPUT, OUTPUT, orSENSOR, that represent the specific function of the PERIPHERAL device.

While the peripheral device 202 has been described to serve as an inputdevice for the host device 201, in other implementations, the peripheraldevice serve other functions as well. For example, the peripheral devicecan be an external speaker that amplifies alarms and alerts triggered bythe hemodialysis machine. The peripheral device is an output device insuch an example. The peripheral device can also be a treatmentaccessory, such as a drug vial or salt solution container. For example,the salt solution container can be a flexible bag with a sensor thatmonitors conductivity of the salt solution within the container. Thecontainer can be paired with the hemodialysis machine such that thecontainer wireless transmits conductivity sensor data to thehemodialysis machine. Peripheral devices can include remote controllers,laptops, desktops, stethoscopes, thermometers, and saline containers,among other dialysis treatment-related peripheral devices.

Referring to the Tap-to-Associate Subroutine described with respect toFIG. 2B, when the operator taps a first device against a second device,the Tap-to-Associate Subroutines of both devices can be triggeredcausing a request to pair to be sent to both devices. In someimplementations, to initiate the pairing, the request is accepted onboth devices. In other implementations, to initiate the pairing, therequest is accepted on at least one of the devices.

Referring to the Pairing Subroutine 313 of FIG. 2B, the operator hasbeen described to manually accept the request sent by the device 200using the second device. In other implementations, the operator canmodify default Pairing Subroutine settings to a manual mode or anautomatic mode. In a manual mode, the operator manually operates thesecond device to accept the request to pair the devices together, asdescribed above. In an automatic mode, the second device canautomatically accept the request to form the NFC connection such thatthe operator just operates the device 200 to form the NFC connection.The request has also been described as a request to establish an NFCconnection between a first device and a second device. The request canalso represent a request to initiate the process of establishing thewireless association. Thus, accepting the request grants permission toboth devices to form the NFC connection, to transmit wireless connectioninformation to one another, and to establish the wireless association.

While information transmitted and stored using the Pairing Subroutinehas been described to be the same regardless of the device label, insome implementations, if one of the devices involved in the PairingSubroutine has a CONNECTOR label, only the device with the CONNECTORlabel stores the connection or identity information of the device towhich it is paired. The device that does not have the CONNECTOR labeldoes not use the connection information, so such implementations reducesthe amount of unused data stored on the device.

While triggering the Tap-to-Associate Subroutine has been described toinitiate the Discover Subroutine and the Pairing Subroutine, in someimplementations, the Tap-to-Associate subroutine only initiates thePairing Subroutine. The operators may manually initiate the DiscoverSubroutine prior to triggering the Tap-to-Associate Subroutine. In someimplementations, the subroutines may not include a Tap-to-AssociateSubroutine. The operator can trigger the Discover and the PairingSubroutines manually using, for example, a user interface on the device.Alternatively, the Discover Subroutine is, by default, automaticallyexecuting and can cause the device to search for nearby devices withwhich to pair. In such implementations, the device can be constantlyscanning for nearby devices with enabled NFC transceivers.

Referring to the Pairing Subroutine, while the operator has beendescribed to accept the request to pair on one device, in someimplementations, the request to pair is accepted on both devices inorder to initiate the pairing subroutine.

Referring back to FIGS. 3A-B, in some implementations, pairings may notautomatically occur between devices as part of the Pairing Subroutine.Rather, a request to pair is first sent prior to establishing thepairing. For example, referring to FIG. 3A, the Pairing Subroutine cancause the peripheral device 202 to send a request to pair with the hostdevice 201. The operator may need to instruct the host device 201 toaccept a pairing request from the peripheral device 202, prompting theNFC connection 304 to be established between the peripheral device 202and the host device 201. The operator can instruct the host device 201to accept the request using, for example, a user interface on the hostdevice 201 or the peripheral device 202.

Referring to the example of FIG. 3B, while the connection device 203 hasbeen described to determine the type of wireless association 310 to formbetween the keyboard 101 and the hemodialysis machine 102 based on thelabels 319 a, 319 c, in some implementations, the connection devicereceives permission from the keyboard and the hemodialysis machine todeliver identifiers and labels to each device. The keyboard and/or thehemodialysis machine then requests the devices linked to the identifiersand determines the type of wireless association based on the labels. Forexample, in some cases, the connection device may not have a wirelesstransceiver. As a result, to initiate a wireless association between afirst device and a second device, the connection device receives anidentifier from a first device and then delivers the identifier to asecond device. The second device then requests to form a wirelessassociation with the device associated with the identifier (i.e. thefirst device).

Referring to FIG. 3B, in some implementations, the connection device canfurther include a Universal Serial Bus (USB) connector so that theconnection device 203 can connect with a device through a USB port.

While the Tap-to-Associate Subroutine has been described to use theacceleration sensed by the sensor system to determine whether a tapmotion has occurred, in some implementations, other sensors of thesensor system can be used that allows an operator to physically triggerthe subroutines. For example, the sensors can be replaced by pushbuttonsthat the operator actuates when the operator associates two devices. Thesensor can also be replaced by pressure sensors, strain sensors, orother sensors that react to physical phenomena that the operator caneasily generate manually. In some implementations, the sensor systemincludes a high-frequency radiofrequency identification (RFID) tag and acorresponding RFID detector. When two devices with the RFID tag anddetector come in close proximity to another, the Tap-to-AssociateSubroutine is triggered. While the Tap-to-Associate Subroutine has beendescribed to be automatically executing, the operator can set thedefault settings such that the operator manually initializes theTap-to-Associate Subroutine of a device. As a result, the operator can,for example, move the device around the room without inadvertentlytriggering the Tap-to-Associate Subroutine. In some examples, a firstdevice triggers the Tap-to-Associate Subroutine by making physicalcontact with a second device.

While the NFC connection 304 are shown as intact in FIG. 3A and the NFCconnections 304 a-b are shown as intact in FIG. 3B, in someimplementations, the devices can sever the NFC connections after formingthe wireless association between the host device and the peripheraldevice. In other implementations, the connection device maintains theNFC connection until a user instructs the connection device to break theconnection.

While the connection device 203 has been described to establish aconnection between two devices, in some implementations, it should beunderstood that the connection device can be used to establishconnections with more than two devices. For example, the connectiondevice can connect with three devices and establish connections betweenall of the three devices. The connection device 203 can be used tocreate wireless associations between more than two devices. For example,the operator can trigger the Tap-to-Associate Subroutine of theconnection device 203 with three or more other devices having HOST orPERIPHERAL labels. The connection device 203 thus receives connectioninformation from the three or more devices. The operator can theninstruct the connection device 203 to form wireless associations betweenthe three or more devices. Based on the labels, the AssociationSubroutine can automatically select the permission granted over thewireless associations. In other implementations, the operator can usethe user interface of the connection device 203 to manually select thepermissions granted by each wireless association.

Referring to FIG. 4A, while the identifiers have been described as IPaddresses, in some implementations, the identifiers can be device names,serial numbers, or other identifying information that can be determinedthrough the wireless network.

Referring to FIGS. 4A-C, while a HOST device such as the hemodialysismachines 102 a-c have been described to have wireless associations withone, two, or three PERIPHERAL devices, it should be understood that aHOST device can accept wireless associations with more than threePERIPHERAL devices. In addition, a PERIPHERAL device can have wirelessassociations with two or more devices. For example, a first PERIPHERALdevice can serve as input devices for two HOST devices. The firstPERIPHERAL device can serve as input devices for two additionalPERIPHERAL devices. A second PERIPHERAL device can serve as an inputdevice for the first PERIPHERAL device.

Referring back to FIG. 4B, the blood pressure cuff 350 a has beendescribed as connected to the keyboard 101 b. In some implementations,PERIPHERAL devices, such as the blood pressure cuff and the keyboard,can have a priority rank. In the cases where a wireless association isformed between two PERIPHERAL devices, the device with the higherpriority rank grants permission to the other device so that the otherdevice can serve as an input. In cases where the two PERIPHERAL deviceshave the same priority rank, the user can indicate instructions to thedevices over a user interface on one of the devices or on the userinterface of another device, such as a smart phone.

A number of embodiments of the invention have been described.Nevertheless, it will be understood that various modifications may bemade without departing from the spirit and scope of the invention.Accordingly, other embodiments are within the scope of the followingclaims.

While only one controller is described, multiple controllers mayalternatively be used.

Implementations of the subject matter and the operations described inthis specification can be implemented in digital electronic circuitry,or in computer software, firmware, or hardware, including the structuresdisclosed in this specification and their structural equivalents, or incombinations of one or more of them. Implementations of the subjectmatter described in this specification can be implemented as one or morecomputer programs, i.e., one or more modules of computer programinstructions, encoded on computer storage medium for execution by, or tocontrol the operation of, data processing apparatus. Alternatively or inaddition, the program instructions can be encoded on an artificiallygenerated propagated signal, for example, a machine-generatedelectrical, optical, or electromagnetic signal, that is generated toencode information for transmission to suitable receiver apparatus forexecution by a data processing apparatus. A computer storage medium canbe, or be included in, a computer-readable storage device, acomputer-readable storage substrate, a random or serial access memoryarray or device, or a combination of one or more of them. Moreover,while a computer storage medium is not a propagated signal, a computerstorage medium can be a source or destination of computer programinstructions encoded in an artificially generated propagated signal. Thecomputer storage medium can also be, or be included in, one or moreseparate physical components or media (for example, multiple CDs, disks,or other storage devices).

The operations described in this specification can be implemented asoperations performed by a data processing apparatus on data stored onone or more computer-readable storage devices or received from othersources.

The term “data processing apparatus” encompasses all kinds of apparatus,devices, and machines for processing data, including by way of example aprogrammable processor, a computer, a system on a chip, or multipleones, or combinations, of the foregoing. The apparatus can includespecial purpose logic circuitry, for example, an FPGA (fieldprogrammable gate array) or an ASIC (application specific integratedcircuit). The apparatus can also include, in addition to hardware, codethat creates an execution environment for the computer program inquestion, for example, code that constitutes processor firmware, aprotocol stack, a database management system, an operating system, across-platform runtime environment, a virtual machine, or a combinationof one or more of them. The apparatus and execution environment canrealize various different computing model infrastructures, such as webservices, distributed computing and grid computing infrastructures.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, declarative orprocedural languages, and it can be deployed in any form, including as astandalone program or as a module, component, subroutine, object, orother unit suitable for use in a computing environment. A computerprogram may, but need not, correspond to a file in a file system. Aprogram can be stored in a portion of a file that holds other programsor data (for example, one or more scripts stored in a markup languagedocument), in a single file dedicated to the program in question, or inmultiple coordinated files (for example, files that store one or moremodules, sub programs, or portions of code). A computer program can bedeployed to be executed on one computer or on multiple computers thatare located at one site or distributed across multiple sites andinterconnected by a communication network.

The processes and logic flows described in this specification can beperformed by one or more programmable processors executing one or morecomputer programs to perform actions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatus can also be implemented as, special purpose logiccircuitry, for example, an FPGA (field programmable gate array) or anASIC (application specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read only memory ora random access memory or both. The essential elements of a computer area processor for performing actions in accordance with instructions andone or more memory devices for storing instructions and data. Generally,a computer will also include, or be operatively coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data, for example, magnetic, magneto optical disks, or opticaldisks. However, a computer need not have such devices. Moreover, acomputer can be embedded in another device, for example, a mobiletelephone, a personal digital assistant (PDA), a mobile audio or videoplayer, a game console, a Global Positioning System (GPS) receiver, or aportable storage device (for example, a universal serial bus (USB) flashdrive), to name just a few. Devices suitable for storing computerprogram instructions and data include all forms of nonvolatile memory,media and memory devices, including by way of example semiconductormemory devices, for example, EPROM, EEPROM, and flash memory devices;magnetic disks, for example, internal hard disks or removable disks;magneto optical disks; and CD ROM and DVD-ROM disks. The processor andthe memory can be supplemented by, or incorporated in, special purposelogic circuitry.

To provide for interaction with a user, implementations of the subjectmatter described in this specification can be implemented on a displaydevice (e.g., the display device of the dialysis machine 12), forexample, a CRT (cathode ray tube) or LCD (liquid crystal display)monitor, for displaying information to the user and a keyboard or keypadand/or a pointing device, for example, a mouse or a trackball, by whichthe user can provide input to the computer. Other kinds of devices canbe used to provide for interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback, forexample, visual feedback, auditory feedback, or tactile feedback; andinput from the user can be received in any form, including acoustic,speech, or tactile input.

Other implementations are within the scope of the following claims.

What is claimed is:
 1. A system comprising: a peripheral device; a first antenna configured to receive a wireless identifier that includes connection information related to the peripheral device via a short-range wireless technology protocol; a second antenna configured for communication via a communication protocol, the communication protocol being other than the short-range wireless technology protocol; and a medical device configured to communicate with the peripheral device via the communication protocol over a wireless connection that is established using the wireless identifier, wherein the peripheral device is granted permission to perform one or both of: (i) monitor one or more treatment parameters of a medical treatment during the medical treatment using the communication protocol, or (ii) control the one or more treatment parameters of the medical treatment during the medical treatment using the communication protocol.
 2. The system of claim 1, wherein the first antenna and the second antenna are either i) parts of the medical device, or ii) provided separate from the medical device.
 3. The system of claim 1, wherein the peripheral device is configured to provide the wireless identifier to the first antenna.
 4. The system of claim 1, wherein the peripheral device and the medical device are configured to establish the wireless connection using the wireless identifier.
 5. The system of claim 1, further comprising a connection device that is configured to provide the wireless identifier to the first antenna.
 6. The system of claim 5, wherein the connection device is configured to establish the wireless connection using the wireless identifier.
 7. The system of claim 5, wherein the connection device has an Internet protocol address.
 8. The system of claim 1, wherein the peripheral device has an Internet protocol address.
 9. The system of claim 1, wherein the peripheral device is a smartphone.
 10. The system of claim 1, wherein the peripheral device comprises one or more of a blood pressure cuff, a thermometer, a stethoscope, or a saline container.
 11. The system of claim 1, wherein the peripheral device comprises a container having a sensor that monitors a characteristic of contents of the container.
 12. The system of claim 11, wherein the contents of the container include a dialysis-related treatment solution.
 13. The system of claim 1, wherein the peripheral device comprises a drug vial.
 14. The system of claim 1, wherein the peripheral device is one or more of a remote controller, a laptop computer, or a desktop computer.
 15. The system of claim 1, wherein the peripheral device is a first peripheral device and the wireless identifier is a first wireless identifier, and wherein the system further comprises a second peripheral device, and wherein the first antenna is configured to receive a second wireless identifier related to the second peripheral device via the short-range wireless technology protocol.
 16. The system of claim 15, wherein the first peripheral device is located at a first distance from the medical device and the second peripheral device is located at a second distance from the medical device, and wherein the medical device is further configured to determine whether the first peripheral device or the second peripheral device is closest to the medical device using the short-range wireless technology protocol.
 17. The system of claim 16, wherein the wireless connection is established with the first peripheral device that corresponds to the first distance that is less than the second distance.
 18. The system of claim 1, wherein controlling the one or more treatment parameters of the medical treatment comprises inputting, into the medical device and via the peripheral device, data related to the one or more treatment parameters.
 19. The system of claim 1, wherein the one or more treatment parameters cause a flow rate to be set or adjusted.
 20. The system of claim 1, wherein the one or more treatment parameters cause a start or stop command to be issued to a pump of the medical device.
 21. A method comprising: establishing a wireless connection between a medical device and a peripheral device; and communicating between the medical device and the peripheral device via a communication protocol over the wireless connection, wherein the peripheral device communicates with the medical device to perform one or both of: (i) monitor one or more treatment parameters of a medical treatment during the medical treatment using the communication protocol, or (ii) control the one or more treatment parameters of the medical treatment during the medical treatment using the communication protocol, wherein the wireless connection is established using a wireless identifier that includes connection information related to the peripheral device, which is received via a short-range wireless technology protocol other than the communication protocol that corresponds to the wireless connection. 